Smart inclusion of technology at time of build

ABSTRACT

Apparatuses, methods, systems, and program products are disclosed for technology management on a hardware component of a device at the time of assembly. An apparatus has a processor and memory storage that stores code executable by the processor. The processor obtains a feature of the hardware component to be removed from the hardware component and operates a virtual fuse that removes a data region associated with the hardware component and permanently removes access to the feature on the hardware component. In response to operating the virtual fuse to remove access to the feature, the processor may indicate the status of the feature on the hardware component.

FIELD

The subject matter disclosed herein relates to computing devices andmore particularly relates to selective resource management of featureson a hardware component at the time of manufacture.

BACKGROUND

Computing devices have various resources on a hardware component enabledthrough firmware and system software for the device. The hardwarecomponent is designed to execute programs, run system software, processdata, or the like. The enabled and disabled features of the hardwarecomponent establish a base model for the computing device.

BRIEF SUMMARY

Apparatuses, methods, systems, and program products are disclosed fortechnology management on a hardware component of a device at the time ofassembly. In one embodiment, an apparatus including a processor and amemory storage device that stores code executable by the processor isdisclosed. The processor operates a virtual fuse that removes a dataregion associated with the hardware component and permanently removesaccess to the feature on the hardware component. In response tooperating the virtual fuse that removes access to the feature, theprocessor may indicate the status of the feature on the hardwarecomponent.

In one embodiment, a method is disclosed. The method obtains a featureof a hardware component to be removed from the hardware component andoperates a virtual fuse that removes a data region associated with thehardware component and permanently removes access to the feature on thehardware component. In response to operating the virtual fuse to removeaccess to the feature, the method may indicate the status of the featureon the hardware component.

In one embodiment, a computer program product is disclosed. The computerprogram product includes a computer-readable storage medium havingprogram instructions embodied therewith. The program instructions obtaina feature of a hardware component to be removed from the hardwarecomponent and operate a virtual fuse that removes a data regionassociated with the hardware component and permanently removes access tothe feature on the hardware component. In response to operating thevirtual fuse to remove access to the feature, the computer program mayindicate the status of the feature on the hardware component.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments illustrated in theappended drawings. Understanding that these drawings depict only someembodiments and are not, therefore, to be considered to be limiting ofscope, the embodiments described and explained with additionalspecificity and detail through the use of the accompanying drawings, inwhich:

FIG. 1 is a schematic block diagram illustrating one embodiment of asystem for hardware component technology feature management duringassembly of the computing device;

FIG. 2 is a schematic block diagram illustrating one embodiment of ahardware component for technology management during assembly of thecomputing device;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus for technology management of a device during assembly of thecomputing device;

FIG. 4 is a schematic flow chart diagram illustrating one embodiment ofa method of managing technology on a hardware component during assemblyof the computing device;

FIG. 5 is a schematic flow chart diagram illustrating optional methodsfor the embodiment shown in FIG. 4 to selectively manage technologyfeatures on a hardware component during assembly of the computingdevice; and

FIG. 6 is a schematic flow chart diagram illustrating optional methodsfor the embodiment shown in FIG. 4 to selectively manage technologyfeatures on a hardware component during the computing device assembly.

DETAILED DESCRIPTION

As appreciated by one skilled in the art, aspects of the embodiments maybe embodied as a system, method, or program product. Accordingly,embodiments may take the form of an entirely hardware embodiment, anentirely software embodiment (including firmware, resident software,micro-code, etc.), or an embodiment combining software and hardwareaspects that may all generally be referred to herein as a “circuit,”“module” or “system.” Furthermore, embodiments may take the form of aprogram product embodied in one or more computer-readable storagedevices storing machine-readable code, computer-readable code, and/orprogram code, referred hereafter as code. The storage devices may betangible, non-transitory, and/or non-transmission. The storage devicesmay not embody signals. In a specific embodiment, the storage devicesonly employ signals for accessing code.

Many of the functional units described in this specification have beenlabeled as modules to emphasize their implementation independence moreparticularly. For example, a module may be implemented as a hardwarecircuit comprising custom VLSI circuits or gate arrays, off-the-shelfsemiconductors such as logic chips, transistors, or other discretecomponents. A module may also be implemented in programmable hardwaredevices such as field-programmable gate arrays, programmable arraylogic, programmable logic devices, or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, comprise one or more physical or logical blocks of executablecode, which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together but may comprise disparate instructionsstored in different locations that, when joined together logically,comprise the module and achieve the module's stated purpose.

A code module may be a single instruction or many instructions and mayeven be distributed over several different code segments, among variousprograms, and across several memory devices. Similarly, operational datamay be identified and illustrated herein within modules and may beembodied in any suitable form and organized within any appropriate datastructure type. The operational data may be collected as a single dataset or distributed over different locations, including othercomputer-readable storage devices. Where a module or portions of amodule are implemented in software, the software portions are stored onone or more computer-readable storage devices.

Any combination of one or more computer-readable mediums may beutilized. The computer-readable medium may be a computer-readablestorage medium. The computer-readable storage medium may be a storagedevice storing the code. The storage device may be, for example, but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,holographic, micromechanical, or semiconductor system, apparatus, ordevice, or any suitable combination of the foregoing.

More specific embodiments (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(RAM), a read-only memory (ROM), an (electronically) erasableprogrammable read-only memory (EPROM, EEPROM, and/or Flash memory), aportable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer-readable storagemedium may be any tangible medium that can contain or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

Code for carrying out operations for various embodiments may be writtenin any combination of one or more programming languages, including anobject-oriented programming language such as Python, Ruby, Java,Smalltalk, C++, or the like, and conventional procedural programminglanguages, such as the “C” programming language, or the like, and/ormachine languages such as assembly languages. The code may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer, or entirely on the remote computer or server. Inthe latter scenario, the remote computer may connect to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all the items are mutually exclusive unlessexpressly specified otherwise. The terms “a,” “an,” and “the” also referto “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may combine in any suitable manner. In the followingdescription, numerous specific details are provided, such as embodimentsof programming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. However, one skilled in the relevant art would recognizethat embodiments may be practiced without one or more of the specificdetails or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments.Each block of the schematic flowchart diagrams and/or schematic blockdiagrams, and combinations of blocks in the schematic flowchart diagramsand/or schematic block diagrams, can be implemented by code. This codemay be provided to a processor of a general-purpose computer, acellphone, a special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor of the computer or other programmabledata processing apparatus, create means for implementing thefunctions/acts specified in the schematic flowchart diagrams and/orschematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, another programmable machine, orother devices to produce a computer-implemented process such that thecode which executes on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which comprises one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may be executedsubstantially concurrently, or the blocks may sometimes be executed inthe reverse order, depending upon the functionality involved. Othersteps and methods may be conceived that are equivalent in function,logic, or effect to one or more blocks, or portions thereof, of theillustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between the illustrated embodiment'senumerated steps. Each block of the block diagrams and/or flowchartdiagrams, and combinations of blocks in the block diagrams and/orflowchart diagrams, can be implemented by particular/special purposehardware-based systems that perform the specified functions or acts orcombinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

An apparatus, in one embodiment, includes a processor and a memory thatstores code executable by the processor. In various embodiments, theapparatus obtains a feature of a hardware component to be removed fromthe hardware component, operates a virtual fuse that removes a dataregion associated with the hardware component and permanently removesaccess to the feature on the hardware component, and indicates thestatus of the feature on the hardware component in response to operatingthe virtual fuse to remove access to the feature.

In one embodiment, the virtual fuse is read by a driver of systemsoftware for the hardware component.

In one embodiment, the firmware of the hardware component has aplurality of data regions. Each data region in the plurality of dataregions is associated with a singular feature of the hardware component.The first feature of the hardware component is permanently removed fromthe hardware component. A second feature of the hardware component ispreserved within the hardware component.

In one embodiment, the virtual fuse erases the data region comprising afirmware for the feature of the hardware component.

In one embodiment, the virtual fuse blows an electronic fuse to anelectronic circuit that controls the feature in the firmware of thehardware component. When the electronic fuse is blown, the electroniccircuit and the hardware component's firmware are not accessible by theprocessor.

In various embodiments, the virtual fuse operates more than one step toremove the data region from the firmware associated with the feature ofthe hardware component. For example, the virtual fuse erases thefirmware of the data region for the feature on the hardware component,writes no-op instructions on the data region of the firmware related tothe feature of the hardware component, and blows a fuse to an electroniccircuit associated with the feature of the hardware component.

The memory storage device can be an Electronically Erasable ProgrammableRead-Only Memory (EEPROM) device in one embodiment. An entirety of theEEPROM device may be erased reprogrammed to remove the data regionassociated with the feature removed from the hardware component. Invarious embodiments, the memory storage device may include EPROM,EEPROM, and/or a flash memory that uses a standard PC voltage to eraseand reprogram the data region associated with the feature removed fromthe hardware component. The virtual fuse may be an external virtual fuseblock located externally from the hardware component having theprocessor and the memory storage device.

One embodiment of a method for selectively disabling technology duringthe device assembly is described. The method includes obtaining afeature of a hardware component to be removed from the hardwarecomponent and operating a virtual fuse that removes a data regionassociated with the hardware component and permanently removes access tothe feature on the hardware component. The method further includesindicating the status of the feature on the hardware component inresponse to operating the virtual fuse to remove access to the feature.

In one embodiment, the method includes operating the virtual fuse towrite no-op instructions on the data region of the firmware for thehardware component that renders the feature of the hardware componentinoperable.

In various embodiments, the method includes operating the virtual fuseto erase the data region, including the firmware for the hardwarecomponent's feature, and/or operating the virtual fuse in other areas ofthe circuit to erase the data region permanently. For example, themethod may operate a virtual fuse that further includes blowing anelectronic fuse to an electronic circuit of the data region associatedwith the feature. In one embodiment, the virtual fuse operates more thanone step to remove the data region from the firmware associated with thefeature of the hardware component. For example, the method may includeerasing the firmware of the data region for the feature on the hardwarecomponent, operating the virtual fuse to write no-op instructions on thedata region of the firmware associated with the feature of the hardwarecomponent, and blowing a fuse to an electronic circuit associated withthe feature of the hardware component.

In various embodiments, the method includes erasing an entirety of anEEPROM device and reprogramming the EEPROM device to remove the dataregion associated with the feature to be removed from the hardwarecomponent. The method may remove the feature using a standard PC voltageto erase and reprogram the data region of an EPROM, EEPROM, and/or flashmemory device associated with the feature removed from the hardwarecomponent.

In various embodiments, an external virtual fuse block that is locatedexternally from the hardware component includes all or part of thevirtual fuse. For example, the method may further include writing no-opinstructions to the data region and/or including firmware for thefeature to be removed from the hardware component. In thisconfiguration, the external virtual fuse block can be retainedseparately from the hardware component.

A computer program product for technology management on a hardwarecomponent of a device at the time of assembly, in one embodiment, has acomputer-readable storage medium with program instructions embodiedtherewith. The program instructions are executable by a processor tocause the processor to obtain a feature of a hardware component to beremoved from the hardware component, operate a virtual fuse that removesa data region associated with the hardware component and permanentlyremoves access to the feature on the hardware component, and indicate astatus of the feature on the hardware component in response to operatingthe virtual fuse to remove access to the feature.

FIG. 1 is a schematic block diagram illustrating one embodiment of asystem 100 for selectively removing technologies from an informationhandling device or a computing device 102 during or at the time of thedevice assembly. In one embodiment, the system 100 includes one or morecomputing devices 102 having one or more circuit boards 104 with varioushardware components 106 that enable various technologies on the circuitboard 104. One or more resource management apparatuses 108 may belocated on the circuit board 104 and/or located on a separate mastermanagement device 110. The system 100 may include one or more datanetworks 112 and/or one or more servers 114.

In one embodiment, the resource management apparatus 108 is located onthe circuit board 104 and communicates with the master management device110 on the server 114. In another embodiment, the resource managementapparatus 108 is located on the server 114 and controls the computingdevice 102. The resource management apparatus 108 may be located on boththe computing device 102 and one or more servers 114. As used herein, aresource management apparatus 108 can include the master managementdevice 110 located on a separate device (e.g., the server 114) and/or aresource management apparatus 108 located directly on the apparatus 200or another location on the computing device 102.

Although a specific number of computing devices 102, circuit boards 104,hardware components 106, resource management apparatuses 108, datanetworks 112, and servers 114 are depicted in FIG. 1, one of skill inthe art would recognize that the system 100 may include any number ofcomputing devices 102, circuit boards 104, hardware components 106,resource management apparatuses 108, master management devices 110, datanetworks 112, and/or servers 114.

In one embodiment, the system 100 includes one or more computing devices102, each having a circuit board 104 with various features 116 encodedwithin the firmware 118 to activate and control various hardwarecomponents 106. Data regions 120 of firmware 118 may provide a mechanismfor controlling all or a part of the functionality, technology, and/orfeatures 116 enabled/disabled on the hardware component 106. In general,enabling a feature 116 makes the technology available to the computingdevice 102 and/or the circuit board 104. Similarly, disabling a feature116 removes the associated technology from the computing device 102and/or the circuit board 104.

The computing devices 102 may be embodied as one or more of a desktopcomputer, a laptop computer, a tablet computer, a smart phone, a smartspeaker (e.g., Amazon Echo®, Google Home®, Apple HomePod®), an Internetof Things device, a security system, a set-top box, a gaming console, asmart TV, a smart watch, a fitness band or other wearable activitytracking device, an optical head-mounted display (e.g., a virtualreality headset, smart glasses, head phones, or the like), aHigh-Definition Multimedia Interface (“HDMI”) or other electronicdisplay dongle, a personal digital assistant, a digital camera, a videocamera, an IoT vehicle (e.g., car, boat, airplane, etc.) or anothercomputing device comprising a processor (e.g., a central processing unit(“CPU”), a processor core, a field programmable gate array (“FPGA”) orother programmable logic, an application specific integrated circuit(“ASIC”), a controller, a microcontroller, and/or another semiconductorintegrated circuit device), a volatile memory, and/or a non-volatilestorage medium, a display, a connection to a display, and/or the like.

FIGS. 1 and 2 illustrate the connection of the resource managementapparatus 108 with the computing device 102 to disable features 116 fromthe hardware component 106. The resource management apparatus 108 isgenerally configured to determine various enabled technologies and/orfeatures 116 and/or disable the selected features 116. A feature 116 isa technology of a hardware component 106 that can be enabled or disabledon the circuit board 104, for example, a video codec and an audio codec.

The resource management apparatus 108 obtains various features 116 ofthe hardware components 106 to be removed from the circuit board 104 andoperates a virtual fuse 122 to selectively remove one or more dataregions 120 associated with the feature 116. This permanently disablesthe feature 116, which is no longer available to the processor. Theresource management apparatus 108 indicates the status of the feature116 on the hardware component 106 in response to operating the virtualfuse 122 and removing access to the indicated the feature 116.

Firmware 118 for the hardware component 106 can have a plurality of dataregions 120. In this configuration, each data region 120 may beassociated with one or more features 116 on the hardware component 106.For example, the data region 120 of a video codec 228 (e.g., first thefeature 116 a) on the hardware component 106 can be permanently removed,and the data region 120 of an audio codec 230 (e.g., second the feature116 b) for the hardware component 106 may be preserved as a feature 116of the hardware component 106.

In this manner, the resource management apparatus 108 may monitor,control, and/or modify the technologies and features 116 available onthe hardware component 106 even after the initial circuit board 104build. For example, the resource management apparatus 108 may modify thefeatures 116 of the circuit board 104 during a computer/cellphoneassembly of a computing device 102.

Since a first company (e.g., a chipmaker) may manufacture the chipsetand/or circuit board 104 at a first facility and a second company (e.g.,a device assembler) may assemble the circuit board 104 in a computingdevice 102 at a second facility, the resource management apparatus 108may reduce exposure to infringement claims to both companies. Theresource management apparatus 108 can modify the enabled features 116after the manufacture of the circuit board 104.

For example, the resource management apparatus 108 can modify features116 during assembly of the computing device 102 and/or remotelyafterward. The server 114 can use the resource management apparatus 108to remotely disable features 116 of the computing device 102 bytargeting data regions 120 of the firmware 118 and/or erasing thefirmware 118 and reinstalling the firmware 116. This feature limits theexposure of the chipmaker and/or the assembler to later claims ofinfringed rights without proper payment for licensing fees. For example,the assembler can enable or disable the technology and features 116 onthe circuit board 104, thereby better controlling the computing devicefeatures sold to the consumer.

In response to disabling a feature 116, the resource managementapparatus 108 may indicate the feature's 116 status on the hardwarecomponent 106. Specifically, the resource management apparatus 108 mayupdate a database and/or use the database to calculate royalties. Thehardware component 106 and/or resource management apparatus 108 candisplay this information to the end-user and/or a manufacturer'srepresentative. The resource management apparatus 108 may indicate toseparate the master management device 110 on the server 114 that thefeature 116 was or was not successfully removed and/or disabled. In oneembodiment, when the resource management apparatus 108 indicates toseparate the master management device 110 that the feature 116 was notsuccessfully removed, a separate master management device 110 connectsto the computing device 102 through the server 114 to remotely disablethe feature 116.

In certain embodiments, the resource management apparatus 108 may bepartially or entirely included on the circuit board 104. Similarly, theresource management apparatus 108 may be partially or entirely installedon the master management device 110. The resource management apparatus108 can control which features 116 are enabled on the circuit board 104.Depending on the enabled technologies of the circuit board 104, themanufacturer (e.g., device assembler) may determine a price for thecomputing device 102 that covers any potential costs of any licensingfees, etc. In addition, the resource management apparatus 108 enablesthe device assembler to offer the same device at different price points,e.g., by disabling unpaid features 116 on a computing device 102.

The resource management apparatus 108 may include a hardware device thatmoderates a hardware component 106 of a circuit board 104. For example,the resource management apparatus 108 may regulate one or more computingdevices 102 such as a secure hardware dongle or other hardware appliancedevice, e.g., a set-top box, a network appliance, etc. In variousembodiments, the computing device 102 may include a head-mounteddisplay, a laptop computer, a server 114, a tablet computer, asmartphone, a security system, a network router or switch, or the like.The resource management apparatus 108 may connect to the computingdevice 102 either by a wired connection (e.g., a universal serial bus(“USB”) connection) or a wireless connection (e.g., Bluetooth®, Wi-Fi,near-field communication (“NEC”), LTE, 5G, or the like).

A hardware device of the resource management apparatus 108 and/or ahardware component 106 on the circuit board 104 may include a powerinterface, a wired and/or wireless network interface, a graphicalinterface that attaches to a display, and/or a semiconductor integratedcircuit device as described below, configured to perform the functionsdescribed herein. The resource management apparatus 108 may beconfigured to control one or more computing devices 102 to selectivelyenable and/or disable various features 116. The resource managementapparatus 108 may create a different product from two physicallyidentical computing devices 102, with each having different features 116enabled and/or disabled.

The resource management apparatus 108 controls the circuit board 104 ofthe computing device 102. The circuit board 104 may include asemiconductor integrated circuit device (e.g., one or more chips, die,or other discrete logic hardware) or the like. The circuit board 104 maybe a field-programmable gate array (“FPGA”) or other programmable logic,firmware for an FPGA or other programmable logic, microcode forexecution on a microcontroller. For example, the circuit board 104 maybe an application-specific integrated circuit (“ASIC”), a processor, aprocessor core, or the like.

In various embodiments, the resource management apparatus 108 has adifferent circuit board 104 than the computing device 102. For example,the resource management apparatus 108 may be located separately and/orexternally from the circuit board 104 of the computing device 102. Inanother embodiment, the resource management apparatus 108 is located onthe circuit board 104 of the computing device 102. For example, theresource management apparatus 108 may be mounted on a printed circuitboard 104 with one or more electrical lines or connections (e.g.,volatile memory, a non-volatile storage medium, a network interface, aperipheral device, a graphical/display interface, or the like).

The hardware component 106 of the circuit board 104 (and/or the hardwaredevice of the resource management apparatus 108) may include one or morepins, pads, or other electrical connections configured to send andreceive data (e.g., in communication with one or more electrical linesof a printed circuit board 104 or the like). One or more hardwarecircuits and/or other electrical circuits may be configured to performvarious functions of the circuit board 104 of the computing device 102and/or the resource management apparatus 108. The resource managementapparatus 108 can electrically couple to the circuit board 104 in thecomputing device 102 and remotely couple to the master management device110 to enable or disable data regions 120 of firmware 118 and turnon/off the circuit board 104 features 116.

The semiconductor integrated circuit device of the circuit board 104,for example, on the computing device 102 (or the hardware device of theresource management apparatus 108) in certain embodiments, includesand/or is communicatively coupled to one or more volatile memory media,which may include but is not limited to random access memory (“RAM”),dynamic RAM (“DRAM”), cache, or the like.

In one embodiment, the semiconductor integrated circuit device, thecircuit board 104, or other hardware appliance of the resourcemanagement apparatus 108 and/or the computing device 102 includes and/oris communicatively coupled to one or more non-volatile memory media,which may include but is not limited to: NAND flash memory, NOR flashmemory, nano random access memory (nano RAM or “NRAM”), nanocrystalwire-based memory, silicon-oxide based sub-10 nanometer process memory,graphene memory, Silicon-Oxide-Nitride-Oxide-Silicon (“SONOS”),resistive RAM (“RRAM”), programmable metallization cell (“PMC”),conductive-bridging RAM (“CBRAM”), magneto-resistive RAM (“MRAM”),dynamic RAM (“DRAM”), phase change RAM (“PRAM” or “PCM”), magneticstorage media (e.g., hard disk, tape), optical storage media, or thelike.

The data network 112, in various embodiments, includes a digitalcommunication network that transmits digital communications, forexample, between a computing device 102 and a server 114 having theresource management apparatus 108 on a separate master management device110. The data network 112 may include a wireless network, such as awireless cellular network, a local wireless network, a Wi-Fi network, aBluetooth® network, a near-field communication (“NEC”) network, an adhoc network, and/or the like. The data network 112 may include a widearea network (“WAN”), a storage area network (“SAN”), a local areanetwork (“LAN”) (e.g., a home network), an optical fiber network, theinternet, or another digital communication network. The data network 112may include two or more networks. The data network 112 may include oneor more servers 114, routers, switches, and/or other networkingequipment. The data network 112 may also include one or morecomputer-readable storage media, such as a hard disk drive, an opticaldrive, non-volatile memory, RAM, or the like.

The wireless connection may be a mobile telephone network. The wirelessconnection may also employ a Wi-Fi network based on any Institute ofElectrical and Electronics Engineers (“IEEE”) 802.11 standards.Alternatively, the wireless connection may be a Bluetooth® connection.In addition, the wireless connection may employ a Radio FrequencyIdentification (“RFID”) communication including RFID standardsestablished by the International Organization for Standardization(“ISO”), the International Electrotechnical Commission (“IEC”), theAmerican Society for Testing and Materials® (ASTM®), the DASH7™Alliance, and EPCGlobal™.

Alternatively, the wireless connection may employ a ZigBee® connectionbased on the IEEE 802 standard. In one embodiment, the wirelessconnection employs a Z-Wave® connection as designed by Sigma Designs®.Alternatively, the wireless connection may employ an ANT® and/or ANT+®connection as defined by Dynastream® Innovations Inc. of Cochrane,Canada.

The wireless connection of data network 112 may be through an infraredconnection, including connections conforming at least to the InfraredPhysical Layer Specification (“IrPHY”) as defined by the Infrared DataAssociation® (“IrDA” 0). Alternatively, the wireless connection may be acellular telephone network communication. All standards and/orconnection types include the latest version and revision of the standardand/or connection type as of this application's filing date.

One or more servers 114 may be embodied as blade servers, mainframeservers, tower servers, rack servers, etc., in one embodiment. The oneor more servers 114 may be configured as mail servers, web servers,application servers, FTP servers, media servers, data servers, webservers, file servers, virtual servers, and/or the like. Servers 114 maybe communicatively coupled (e.g., networked) over a data network 112 toone or more computing devices 102 and may be configured to execute orrun machine learning algorithms, programs, applications, processes,and/or the like.

As described in greater detail below, a computing device 102 can have anextensive supply chain. For example, the supply chain may include thechipset manufacturers (aka chipmakers), logic board manufacturer and/orcircuit board 104 assembler, and/or device makers/assemblers. Themanufacturers of the computing device 102 work together to manufactureand distribute a circuit board 104 on a particular computing device 102.Generally, manufacturers and assemblers in the supply chain attempt toobtain any pertinent licenses from the relevant patent holders prior tointroducing a new circuit board 104 and/or computing device 102 to themarket.

For example, a hardware component 106 (e.g., a chip on the circuit board104) may use various industrial standards/technologies that are licensedand protected. Many such features have become industry standards and mayuse a FRAND fee agreement and/or another agreed-upon licensingarrangement.

As used herein, “manufacturer” refers to any organization or entityalong the supply chain, from the fabrication of a chip or anothercomponent to a consumer-ready product. A “chipmaker” is the particularmanufacturer of the circuit board 104, and a device assembler assemblesthe viable consumer product utilizing the circuit board in a computingdevice 102 that is sold to the end-user as a product (e.g., laptop orcellphone).

Given the scale of the various technologies and functions on eachhardware component 106 and the different configurations of each circuitboard 104, manufacturers often seek to obtain a broad technology licensebefore releasing a new product, e.g., cellphone, computer, or laptop.However, this can be costly if certain technologies and/or features arenot desirable for a particular circuit board 104. In various embodimentsdescribed below, the chipmaker may include a new technology on a circuitboard 104, which the device assembler (and/or consumer) decides not toinclude in the device. Previously, to disable a feature 116 on a circuitboard 104, device assemblers would design and order a new circuit board104 without the technology. This practice adds significant model/SKUcomplexity for tracking the physical orders of old and new circuitboards 104 with and without the functional capability. However, theability to permanently disable features enables the device assembler tocreate similar physical consumer models having different digitalarchitectures. The configuration may also enable more specificity forlicensing surcharges since the digital architecture is known.

The number of technologies for each hardware component 106 may makevariations in just one or two features 116 too significant of a timecommitment to renegotiate licensing fees, e.g., for “small” feature 116variations. However, including unused technologies on each circuit board104 may result in substantial cost increases for the computing device102. In some embodiments, the increased costs may be justified since thecosts may be small, or the consumer may want the added features 116.However, in other embodiments, these features may only increase the costof the computing device 102 (e.g., for licensing fees) for which thetechnology will not be used or accessed.

Chipmakers sometimes attempt to fuse features 116 on the circuit board104 to remove a feature 116, but this practice increases the complexityfor the device assembler. For example, the device assembler needs tocreate a separate SKU for each modified circuit board 104 and track themodified functionality and features of each SKU for the circuit board104. The device assembler may also need to pay for licenses for thedisabled features 116, which may increase the cost of the computingdevice 102 to the end consumer.

Some examples of feature fusing may include eFuses and/or externalresistors. Both eFuses and external resistors operate by increasing theresistance to the features 116 on the physical, electronic circuit. Thismay increase the chip's cost and/or remove die space for other hardwarecomponents 106 and are not generally software configurable. A circuitboard 104 combining several eFuses for several codecs (e.g., features116) could add significant cost to the hardware component 106 and/or thecircuit board 104. Since chipmakers may not want to alter the design ofthe circuit board 104 or add the eFuses proposed by the device assemblerto enable or disable technologies, device assemblers are often unable tofulfill specific customer requests for enabling or disabling specifictechnologies. The cost of redesigning a circuit board 104 without theenabled features can become cost-prohibitive. Accordingly, there is aneed from the perspective of the device assembler and end-user that thechip supplier provides a mechanism to either enable or disable desiredfeatures on the circuit board 104 at the time of assembly.

The Applicant has found a smart inclusion/exclusion method for granularcontrol of technologies and/or features 116 on a hardware component 106.The method can selectively enable/disable various technologies and/orfeatures of the hardware component 106 after the circuit board has beenbuilt. The selective inclusion of various technologies (e.g., features116) allows chipmakers and device assemblers to target the desiredtechnology and/or features 116 for client-driven systems where thefunctionality justifies the cost. In other words, the selective feature116 inclusion/exclusion on the circuit board 104 advances marketplacecompetition by providing the consumer a broader assortment oftechnologies available on the hardware components 106 of a computingdevice 102. This enables more efficient distribution of new technologiesfor the models/users that are willing to pay for the new features 116,while also providing a broader assortment of computing productsavailable to customers to customize the desired technologies andfeatures 116 for their individual needs and/or practice.

The Applicant has found that these systems and methods enable the deviceassemblers to order commercially available standard circuit boards 104from the chipmaker and build various devices from the same standard baseconfiguration. The device assembler can create new virtual SKUs and/orcircuit boards 104 based on the model's base configuration, submodel,and/or location (e.g., country) to enable/disable various technologyfeatures 116 for that product family. Further, theenablement/disablement method cannot be later modified by theend-consumer. The system and method can ensure that the enabled features116 have the proper licenses. This may also prevent the distribution ofunlicensed technology by either the chipmaker or the device assembler.

In one embodiment, the chipmaker can set a one-time “virtual fuse” thatthe device assembler can modify. For various models, sub-models, orcountries where different technologies are required, the virtual fusecan be adjusted at the time of assembly. When the virtual fuse is “on,”the hardware feature 106 technology is enabled, and the feature 116 isavailable technology for that the computing device 102. If, in contrast,the virtual fuse is “off,” then the technology remains disabled andcannot be enabled by the end-user. For example, the firmware for thattechnology is “bricked.”

The Applicant has found that an external fuse block 124 on a resourcemanagement apparatus 108 located off the circuit board 104 and/or awrite-once/one-time programmable storage on the circuit board 104 of thecomputing device 102 can be used to selectively enable/disable features116 during the assembly of the computing device 102.

The chipmaker can establish enabling/disabling values for the hardwarefeature 106 in a software-driven process during the chip's manufacturein one embodiment. The device assembler can use a resource managementapparatus 108 configured for the particular circuit board 104 toselectively enable/disable features of the computing device 102 duringthe assembly. The resource management apparatus 108 can send a bitand/or code to hardware components 106 to enable or disable variousfeatures. Since the resource management apparatus 108 can be storedexternally from the circuit board 104, the supply chain's overallcomplexity for both the chipmaker and the devise assembler may besimplified.

In another variation, an embedded firmware 118 on the circuit board 104may include a special and/or unique program to create a permanentvirtual switch or virtual fuse 122. The virtual fuse 122 is storedwithin a data region 120 of the firmware 118 and either enables ordisables the technology. The data region 120 selectively enables thefirmware 118 of the component or “bricks” the component so that theprocessor 204 and/or the circuit board 104 cannot access it.

During the circuit board 104 manufacturing, the chipmaker can installthe virtual switch by installing the program into the data region 120 ofthe firmware 118. The device assembler can use a resource managementapparatus 108 to control the hardware component 106 and may eitherdisable or enable various features 116. Virtual fuse 122 can temporarilyor permanently change the state of a bit in the data region 120 andselectively disable the technology and/or the feature 116 on the circuitboard 104. Virtual fuse 122 may access a memory storage device 126 ofthe hardware component 106 and/or directly modify data regions 120 offirmware 118.

After the bit is changed/written in the data region 120 of the firmware118, a virtual fuse 122 of the resource management apparatus 108 canfurther operate on the hardware component 106 to reprogram the firmware118 and/or otherwise modify the circuit board 104. On initial startup,the resource management apparatus 108 may send a bit or code thatchanges the bit only once and either permanently erases the data region120 or enables the feature 116 on the hardware component 106. Once thebit is written to and/or erased from the data region 120 of the firmware118, the state of the hardware component 106 cannot be changed. In oneembodiment, the resource management apparatus 108 sends a code thatcauses the data region 120 of the firmware 118 to write no-op codes.

At system boot and/or reset, the embedded firmware 118 on either thehardware component 106 or the circuit board 104 reads the virtual fuse122. When the virtual fuse is on, the technology feature is enabled. Incontrast, when the virtual fuse 122 is off, the feature 116 is disabledfor the hardware component 106. The processor 204 and/or the circuitboard 104 can determine whether the feature 116 has been permanentlydisabled by reading virtual fuse 122. Similarly, drivers or othercomponents may read the virtual fuse 122 settings as needed.

Since the firmware 118 is a trusted system component, the chipmakerand/or device assembler can track the data region 120 (e.g., in theresource management apparatus 108 and/or register module 304 ofapparatus 300 shown in FIG. 3). The chipmaker and/or device assemblerscan later verify and attest that the sold configuration was licensed,secured, and unmodified. Further, the firmware lifecycle may be enhancedby including this self-modifying the data region 120 and modifying itwith a virtual fuse 122 that selectively enables or removes the firmware118 for one or more features 116 in the data region 120. For example,keeping the resource management apparatus 108 on another device separatefrom the circuit board 104 ensures that the manufacturing codes and/orbits to modify data regions 120 of firmware 118 remain secure.

FIG. 2 is a schematic block diagram of an apparatus 200 comprisingvarious hardware components 106. The apparatus 200 has hardwarecomponents 202 that may be functionally the same or similar as thecircuit board 104 having hardware components 106. In variousembodiments, hardware components 202 of the apparatus 200 can includeprocessors 204 (e.g., a central processing unit or CPU 206, anotherprocessor 204 or processor core, a field-programmable gate array(“FPGA”) or other programmable logic, an application-specific integratedcircuit (“ASIC”), a controller, a microcontroller, and/or anothersemiconductor integrated circuit device). The apparatus 200 includes aCPU 206 and various processors 204. Processor 204 includes CPU 206 butmay also include additional processing cores or processors 204 on theapparatus 200. Stated differently, CPU 206 is a specialized processor204, but other processors 204 may be included on the apparatus 200.

The apparatus 200 can also include a memory storage device 208 havingvarious memory addresses 210 for volatile memory or RAM 212, and/or anon-volatile storage medium, e.g., ROM 214. In various embodiments,memory storage device 208 may include an erasable electronic read-onlymemory or EEPROM device 216. The memory storage device 208 may haveaddresses 210 for data regions 220 of firmware 222, system software 224(e.g., an operating system), and/or other programs run by processor 204.Additional hardware components 202 of the apparatus 200 may include agraphics card or GPU 226 having a video codec 228 and/or an audio codec230, an RF Transceiver 232, a camera image signal processor 234, a NearField Communications (NFC) wireless subsystem 236 including a Bluetoothsubsystem 238 and a Wi-Fi subsystem 240, a digital signal processor orDSP 242, an artificial intelligence neural network or AI engine 244, amodem 246, such as a cellular modem 248, and connections to USB ports252 and the like.

For example, the apparatus 200 can have a charging port 250, a securitysupport system 254, and/or cellular technology (e.g., a cellular modem248). As used herein, various components are shown on a single component(e.g., video codec 228 and audio codec 230 on GPU 226) can be separatedonto one or more different hardware components 202.

Various data regions 220 may have different addresses 210 on theapparatus 200 and/or the hardware component 202 that encode varioustechnologies. Virtual fuse 256 can target one or more specific addresses210 for data regions 220 encoding firmware 222 for features 260 on theapparatus 200. FIG. 2 shows one exemplary embodiment of the apparatus200 having several hardware components 202 and features 260, but itshould be recognized that other hardware components 202, features 260,and/or configurations of the apparatus 200 are within the scope of thepresent disclosure.

Each hardware component 202 includes data regions 220 storing thefirmware 222 configured to enable one or more features 260 tocommunicate with the CPU 206, the processors 204, and/or the systemsoftware 224 on the apparatus 200. For example, data regions 220 and/orfirmware 222 may be stored on a non-volatile memory storage device 208,such as an EPROM device, an EEPROM device, and/or a flash memory device.The CPU 206 may utilize the system software 224 that communicates withand thereby utilizes the various enabled technologies and/or features260 of each hardware component 202. For example, the system software 224may enable and/or enhance video codec 228 on GPU 226 throughinteractions of the CPU 206 with the data regions 220 of firmware 222.

The system software 224 may be run by the CPU 206 and/or otherprocessors 204 to communicate and/or control features 260 of connectedhardware components 202. The system software 224 may be a processor-sideapplication 262 that facilitates and/or enables the communicationbetween the CPU 206 and various hardware components 202. As used herein,firmware 222 is a client-side code stored on the hardware component 202that enables the hardware component 202 to communicate with the CPU 206and/or the apparatus 200. The system software 224 may include orinterface with firmware 222 of the hardware component 202. The firmware222 installed on the hardware component 202 may enable various features260 of the hardware component 202 that can be operated by the CPU 206and/or other processors 204.

The hardware component 202 includes one or more data regions 220 in thefirmware 222 to selectively enable or disable the features 260 of thehardware component 202. The data regions 220 provide selectivity forfeatures 260 on the apparatus 200 and enable granular specificity forenabled or disabled features 260. The apparatus 200 functionality is acompilation of the variation and quantity of the enabled features 260 onthe hardware components 202 and the ability to control/use the hardwarecomponent 202 through system software 224.

For example, video codec 228 of GPU 226 enhances the apparatus 200 byproviding a standardized format for communicating with the systemsoftware 224. When properly configured with the appropriate firmware222, GPU 226 enhances the apparatus 200 with the various features 260provided by the video codec 228 to compress/decompress, communicate,transmit, and/or display video signals. However, each of these features260 is only available to the apparatus 200 if the data region 220 isenabled and the appropriate firmware 222 is installed and readable bythe system software 224 for the specific video codec 228 and/or GPU 226feature.

Similarly, NFC wireless subsystems 236 use a standardized andappropriate firmware 222 to enable various features 260 for a Bluetoothsubsystem 238 and/or Wi-Fi subsystem 240. In one embodiment, the enableddata region 220 of the firmware 222 may enable the apparatus 200 to have5G cellular capability the feature 260, whereas the same the apparatus200 without this firmware 222 (e.g., a bricked data region 220) wouldonly have access to a 4G spectrum. The Wi-Fi subsystem 240 may includeanother data region 220 with different firmware 222 for a Wi-Fi 6-readythe feature 260 compared to 802.11a/b/g, or 802.11n Wi-Fi features 260.

One feature of this application is a device assembler's ability toenable and/or disable various features 260 after the apparatus 200construction and thereby modify a digital architecture 264 withoutchanging the physical architecture 266 of the apparatus 200. Forexample, the same apparatus 200 can include a cellular modem 248 thatsupports both 4G and 5G features 260 but have only 4G features enabled.This may make the cellphone more affordably by not necessitating a newapparatus 200 design and/or reducing the cellphone device's licensingfees.

The enablement of different features 260 on the apparatus 200 mayinclude costs, such as design and testing costs and/or licensing feesfor the various enabled technologies. This can increase the total costof the apparatus 200 and/or the computing device 102. The consumer mayopt to pay a reduced cost for a computing device 102 with certainfeatures 260 disabled.

However, previously, manufacturers and/or assemblers have lackedgranularity on the specific individual enabled features 260 sold to theuser. This meant the assembler might pay to license all the features 260regardless of whether they were enabled or used. The Applicant has foundthat the ability to disable various technologies and/or features 260selectively and permanently on an apparatus 200 provides themanufacturer the benefit of mass production of the same designedapparatus 200. This feature also provides the end-consumer the selectivevariability for desired features 260 on a particular computing device102. The cost of designing and manufacturing different virtual SKUproducts is more efficient than physically changing the structures onthe circuit board 104. The consumer also has greater access to thedesirable features 260 for a particular application without paying forundesired technologies.

Selectively and permanently disabling features 260 after manufacture(e.g., during assembly of the computing device 102) enhances the abilityto mass-produce an apparatus 200 the physical apparatus 200. Theselectivity also permits a broad assortment of features 260 in thedigital architecture for end-user selection. Because the resourcemanagement apparatus 108 indicates whether the technology wassuccessfully removed in response to operating a virtual fuse, the mastermanagement device 110 on a remote server 114 may maintain a list ofenabled features 260 on each computing device 102. If the assemblerand/or manufacturer is later accused of patent infringement, they canaffirmatively demonstrate which features were paid for (e.g., licensed)and enabled and which features were permanently disabled on theapparatus 200. Enabling the manufacturer and/or assembler tomass-produce/purchase the same physical architecture 266 on theapparatus 200 also provides a broader assortment of different features260 to the consumer.

FIG. 3 is a schematic block diagram illustrating one embodiment of acircuit board 104 or apparatus 300 with enabled features 260 onindividual hardware components 202. A setup module 302 (e.g., theresource management apparatus 108 operating on system software 224 ofthe information handling device) may include code executable onprocessor 204 to enable/disable data regions 220 of firmware 222 ofvarious hardware components 202. Setup module 302 includes a registermodule 304, a designation module 306, a fuse block module 308, and arecording module 310.

With reference to FIGS. 2 and 3, the apparatus 300 has processor 204electronically coupled to a memory storage device 208 and each hardwarecomponent 202. The processor 204 receives instructions from the resourcemanagement apparatus 108 to control various features 260 of theapparatus 200. Specifically, the setup module 302 may include individualmodules (e.g., register module 304, target feature module 306, fuseblock module 308, recording module 310, register store 312, etc.) thatfunction to enable and/or disable various features 260 provided by thehardware components 202 on the apparatus 200. In various embodiments,the virtual fuse 256 can modify and/or change the digital architecture264 of the apparatus 200 without affecting the physical architecture 266of the apparatus 200.

For example, a setup module 302 can execute code and/or send a bit to adata region 220 of the firmware in a hardware component 202. In responseto receiving the bit, the data region 220 encodes whether to enable ordisable the feature 260 of the hardware component 202. When the feature260 is enabled, the data region 220 encodes the firmware 222 for thefeature 260. When the feature is disabled, the bit runs a program storedin the data region 220 to brick all or part of the chip and permanentlyremove the apparatus 200 and/or processor 204 access to the feature(s)controlled by the data region 220 on the hardware component 202. Inanother embodiment, the data region 220 operates a physical orelectronic fuse 268 and permanently alters (e.g., removes and/ordestroys) access to the circuit encoding the feature 260 of the hardwarecomponent 202. In yet another example, the virtual bit first encodes thedata region 220 to remove access to a feature 260 and then operates theelectronic fuse 268 to alter access to the data region 220 permanently.

The virtual fuse 256 can blow an electronic fuse 268 to an electroniccircuit 270 that controls the feature 260 by writing and/or erasingcodes firmware 222 of the hardware component 202. Once the electronicfuse 268 is blown, the electronic circuit 270 and the firmware 222 forthe feature 260 of the hardware component 202 are not accessible to theprocessor 204. In various embodiments, the virtual fuse can write randombits and/or no-op codes in the data region 220 of the firmware 222,encoding the feature 260 of the hardware component to be removed.Virtual fuse 256 may erase the data region 220 and/or the firmware 222for the feature 260 from the hardware component 202 and/or blow anelectronic fuse 268 and/or electronic fuse 268 of the electronic circuit270 controlling the feature 260 of the hardware component 202. Forexample, the electronic fuse 268 and/or electronic fuse 268 can beelectronically coupled to the data region 220 of the firmware 222 or aparticular portion of the hardware component 202 and/or firmware.

Memory storage device 208 stores executable code accessible to setupmodule 302 to control features 260 of hardware components 106 on theapparatus 200 by the processor 204. A register module 304 stores arecord of hardware components 106 and/or features 260 of hardwarecomponents 106 on the apparatus 200. In some embodiments, registermodule 304 maintains a register store 312 for each enabled feature 260of each hardware component 202 on the apparatus 200. For example,register module 304 records a firmware 222 configuration (e.g., version,update history, and/or compatibility) of each hardware component 202 andthe features 260 enabled by the firmware 222. Register module 304 mayinclude configurations and/or bit codes or keys for enabling and/ordisabling firmware 222 and associated features of hardware components106.

In various embodiments, an operator of apparatus 300 designates afeature 260 of the hardware component 202 to be removed from theapparatus 200. In embodiments, the setup module 302 can obtain thefeatures 260 from either a human operator or a programmatic input, suchas a setup module 302 for the features 260 of the apparatus 200 to beadded and/or removed. For example, in one embodiment, an operatorselects a specific feature 260 to be disabled on the apparatus 200, andthe setup module 302 either recommends and/or determines a differentrelated feature to enable/disable on the apparatus 200. Once apparatus300 obtains the features 260 to enable/disable, a fuse block module 308operates a virtual fuse 256 that sends one or more bits, e.g., to thefirmware 222, and permanently remove access to the designated feature260 of the hardware component 202 on the apparatus 200. Virtual fuse 256can send a binary signal comprising one or more bits written to thefirmware 222 of the hardware component 202 to either enable and/ordisable the designated feature 260. In some embodiments, a bit (orbinary signal) is sent to firmware 222 of the hardware component 202 andwritten in firmware 222 of the hardware component 202 to create virtualfuse 256 that disables access by processors 204 of the apparatus 200from accessing either the designated the feature 260 and/or part or allof the hardware component 202.

In response to virtual fuse 256 of fuse block module 308 removing accessfrom processor 204 to the designated feature 260, recording module 310removes or deletes the feature 260 of the hardware component 202 fromregister store 312. In other words, recording module 310 amends theregister store 312 to include only enabled features 260 of the apparatus200. Recording module 310 can transmit a copy of the enabled features260 on register store 312 to system software 224 and/or setup module302. For example, a manufacturer or assembler of a computing device 102that incorporates the apparatus 200 may store a copy of the enabledfeatures 260 associated with an SKU for the apparatus 200. A virtualfuse 256 may alter firmware 222 on a hardware component 202 toenable/disable features 260 on the apparatus 200 selectively provides anapparatus 200 with the same or similar mass-produced physicalarchitecture 266 with a varied digital architecture 264. The ability toselectively enable/disable features of the apparatus 200 aftermanufacture but during assembly, for example, enables an assembler tomodify the circuit board 104 produced by the manufacturer for thespecific consumer while also ensuring that appropriate licensing feesand/or other costs of the technology are appropriated associated withthe SKU of the apparatus 200.

In various embodiments, device drivers, system software 224, installedprograms, and/or other components coupled to processor 204 may read theregister store 312. For example, the system software 224 may read theregister store 312 to determine whether the virtual fuse 256 isenabled/disabled for a driver of the apparatus 200. In anotherembodiment, the register store 312 includes a list of all the hardwarecomponents 202 and their associated features 260 on the apparatus 200and modifies the register store 312 of available features 260 and/or thehardware components 202 when each is removed by the virtual fuse 256.

The register store 312 may read the data regions 120 of the firmware 222on the hardware component 202. For example, the register store 312 canread whether a first feature 116 a of the hardware component 202 ispermanently removed and read a second feature 116 b of the hardwarecomponent 202 that is preserved on the apparatus 200. The recordingmodule 310 can then update and/or maintain the register store 312.

In various embodiments, the memory storage device 208 encoding thefirmware 222 is stored in electrically erasable programmable read-onlymemory (EEPROM) and/or an elastic flash read-only memory. The memorystorage device is a stock Read-Only Memory (“stock ROM”) device in otherembodiments. EEPROM, flash, and/or stock ROM include a firmware 222 foreach hardware component 202 on the apparatus 200. The system software224 of one or more computing devices 102 can use the firmware 222located on the hardware component 202 to control one or more features260 of the hardware component 202. In various embodiments, the virtualfuse 256 operates on EPROM, EEPROM, flash memory, and/or stock ROM andthereby creates a new virtual apparatus 200 by controlling which dataregions 120 on the firmware 222 are accessible. Virtual fuse 256 cancontrol access to features 260 on the hardware component 202 and therebychanges the digital architecture 264 of the apparatus 200.

In some embodiments, the virtual fuse 256 is an external virtual fuseblock 124 that is located externally from the apparatus 200 that has theprocessor 204 and the memory storage device 208. The manufacturer orassembler may retain the external virtual fuse block 124 of the hardwarecomponent 202.

FIG. 4 is a schematic block diagram illustrating a method 400 forselectively disabling features 260 on the apparatus 200 during assemblyof a computing device, e.g., after the manufacture of the apparatus 200.In one embodiment, method 400 includes obtaining 402 a feature 260 of ahardware component 202 to be removed from the apparatus 200 andoperating 404 a virtual fuse 256 that removes a data region 220associated with the hardware component 202. In various embodiments,virtual fuse 256 may permanently remove access to the feature 260 on theapparatus 200. In response to operating the virtual fuse 256 to removeaccess to the feature 260, the method may include indicating 406 astatus of the feature 260 on the hardware component 202. For example,the resource management apparatus 108 may indicate the feature 260 isdisabled to a user-display and/or to separate the master managementdevice 110 on a server 114.

FIG. 5 is a schematic block diagram illustrating various optionalmethods 500 of the method 400 shown in FIG. 4 for selectively disablingfeatures 260 on the apparatus 200 at the time of assembly. Method 500may operate 502 the virtual fuse 256 to erase the data region 220comprising firmware 222 for the feature 260 of the hardware component202. Method 500 may include operating 504 the virtual fuse 256 to writeno-op instructions in the data region 220 of the firmware 222 for thehardware component 202. The no-op instructions render the feature 260 ofthe hardware component 202 inoperable. In some embodiments, operating506 the virtual fuse 256 may blow an electronic fuse 268 to anelectronic circuit 270 of the data region 220 associated with thefeature 260. In various embodiments of method 500, a single virtual fuse256 may operate some or all steps 502 through 506.

Virtual fuse 256 may erase 508 an entirety of a memory device 208, suchas the EPROM device, the EEPROM device 216, and/or the flash memorydevice 218. Virtual fuse 256 may reprogram the memory device 208 (e.g.,EEPROM device 216 and/or flash memory device 218) to remove the dataregion 220 associated with the feature 260 to be removed from theapparatus 200. In another embodiment, virtual fuse 256 uses a standardPC voltage to erase and reprogram 510 the data region 220 of the memorydevice 208 (e.g., the EEPROM device 216 or the flash memory device 218)associated with the feature 260 to be removed from the apparatus 200.

In one embodiment, the virtual fuse 256 is an external virtual fuseblock 124 located externally from the apparatus 200. External virtualfuse block 124 may send a bit to a data region 220 of firmware 222associated with the feature 260 to be removed from the hardwarecomponent 202. The virtual fuse block 124 can write no-op instructionson the data region 220 for the firmware 222 of the feature 260 to beremoved from the hardware component 202. In this way, the externalvirtual fuse block 124 can be retained separately. This configurationmay help the manufacturers, chipmakers, and/or device assemblers controland/or monitor the external virtual fuse block 124. In variousembodiments, the manufacturer and/or assembler of the hardware component202 retains external virtual fuse block 124. In various embodiments, theenabled/disabled features on apparatus 200 may be stored and/or recorded512 in a database. For example, the enabled features 260 in data region220 may be stored in a database on server 114 and/or in resourcemanagement apparatus 108. Server 114 may record the disabled features260 in data region 220 of hardware component 202.

FIG. 6 is a schematic block diagram illustrating various optionalmethods 600 of the method 400 shown in FIG. 4 for selectively disablingfeatures 260 on the apparatus 200 at the time of assembly. In variousembodiments, method 600 operates 602 an external virtual fuse block 124that is external from the apparatus 200 and comprises the virtual fuse256. Method 600 may write 604 no-op instructions to the data region 220of the firmware 222 for the feature 260 to be removed from the hardwarecomponent 202. Method 600 may maintain 606 the register store 312 ofenabled features on the apparatus 200. In other words, register store312 maintains a record of enabled features 260 on the apparatus 200accessible by processor 204 and/or an operator of the system/method. Inresponse to the virtual fuse 256 permanently removing processor 204access to the feature 260, method 600 can remove 608 the feature 260from register store 312. Register store 312 can store a list or registerof all the enabled features 260 of each hardware component 202 on theapparatus 200. Similarly, register store 312 can store a list of eachdisabled feature 260 for a particular SKU of the apparatus 200.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. Therefore, the scope of the invention is indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. An apparatus, comprising: a processor; and amemory storage device that stores code executable by the processor to:obtain a feature of a hardware component to be removed; operate avirtual fuse that removes a data region associated with the hardwarecomponent and permanently removes access to the feature; and indicate astatus of the feature on the hardware component in response to operatingthe virtual fuse to remove access to the feature.
 2. The apparatus ofclaim 1, wherein the virtual fuse is read by a driver of a systemsoftware.
 3. The apparatus of claim 1, wherein a firmware of thehardware component has a plurality of data regions, wherein each dataregion in the plurality of data regions is associated with a singularfeature of the hardware component, and wherein a first feature of thehardware component is permanently removed and a second feature of thehardware component is preserved.
 4. The apparatus of claim 1, whereinthe virtual fuse erases the data region comprising a firmware for thefeature of the hardware component.
 5. The apparatus of claim 1, whereinthe virtual fuse blows an electronic fuse to an electronic circuit thatcontrols the feature of the hardware component, wherein when theelectronic fuse is blown, the electronic circuit and the firmware of thehardware component are not accessible by the processor.
 6. The apparatusof claim 1, wherein the virtual fuse: writes no-op instructions on thedata region of the firmware associated with the feature of the hardwarecomponent; or erases the firmware of the data region for the feature onthe hardware component; and blows a fuse to an electronic circuitassociated with the feature of the hardware component.
 7. The apparatusof claim 1, wherein the memory storage device is an ElectronicallyErasable Programmable Read-Only Memory (EEPROM) device, wherein theEEPROM device is at least partially erased and reprogrammed to removethe data region associated with the feature to be removed.
 8. Theapparatus of claim 1, wherein the memory storage device comprises flashmemory that uses a standard PC voltage to erase and reprogram the dataregion associated with the feature to be removed.
 9. The apparatus ofclaim 1, wherein the virtual fuse is a virtual fuse block that isexternal from the hardware component having the processor and the memorystorage device.
 10. The apparatus of claim 9, wherein the external fuseblock is retained separately on a server.
 11. A method, comprising:obtaining a feature of a hardware component to be removed from thehardware component; operating a virtual fuse that removes a data regionassociated with the hardware component and permanently removes access tothe feature on the hardware component; and indicating a status of thefeature on the hardware component in response to operating the virtualfuse to remove access to the feature.
 12. The method of claim 11,wherein operating the virtual fuse writes no-op instructions the dataregion comprising a firmware for the hardware component that renders thefeature of the hardware component inoperable.
 13. The method of claim11, wherein operating the virtual fuse erases the data region comprisinga firmware for the feature of the hardware component.
 14. The method ofclaim 11, wherein operating the virtual fuse further comprises blowingan electronic fuse to an electronic circuit of the data regionassociated with the feature.
 15. The method of claim 11, whereinoperating the virtual fuse further comprises: writing no-op instructionson the data region of the firmware associated with the feature of thehardware component; or erasing the firmware of the data region for thefeature on the hardware component; and blowing a fuse to an electroniccircuit associated with the feature of the hardware component.
 16. Themethod of claim 11 further comprises erasing an EEPROM device andreprogramming the EEPROM device to remove the data region associatedwith the feature to be removed from the hardware component.
 17. Themethod of claim 11, further comprising using a standard PC voltage toerase and reprogram the data region of a flash memory device associatedwith the feature to be removed from the hardware component.
 18. Themethod of claim 11, further comprising a virtual fuse block that isexternal from the hardware component and comprises the virtual fuse,wherein the method further comprises writing no-op instructions to thedata region comprising a firmware for the feature to be removed from thehardware component.
 19. The method of claim 18, wherein the externalvirtual fuse block is retained on a server and separate from thehardware component.
 20. A computer program product, comprising acomputer-readable storage medium having program instructions embodiedtherewith, the program instructions are executable by a processor tocause the processor to: obtain a feature of a hardware component to beremoved from the hardware component; operate a virtual fuse that removesa data region associated with the hardware component and permanentlyremoves access to the feature on the hardware component; and indicate astatus of the feature on the hardware component in response to operatingthe virtual fuse to remove access to the feature.